Items filtered by date: Monday, 07 December 2015

This has not been replace by a 2011 version search this site for updated instructions

1. Download Windows Live Installer from download.live.com.
2. Install or upgrade the Windows Live Messenger to latest version.
3. Open Windows Explorer, and set it to Show hidden files and folders and show protected operating system files (uncheck the tick for Hide protected operating system files) in the View tab of Folder Options.
   
   In Windows Vista, run Windows Explorer as Administrator, and user may requires to take ownership and gain full control permissions for the folders below before able to access them.
4. Browse to \Program Files\Common Files\Windows Live\.cache\ folder.
5. There will be a lot of folders made up of 15 characters and numbers. Locate Messenger.msi file inside one of the folder. Messenger.msi is the individual separate standalone setup installer for Windows Live Messenger 2009, which can be backed up or copied to another location. Do note that the Messenger.msi and other Windows Installer Package retrieved this way is silent installer.
   
   Tip: %ProgramFiles%\Common Files\Windows Live\.cache\cache.ini file contains the paths of all Windows Live software products downloaded or installed on the computer.
    
6. If you have any problem with Windows Live Messenger after installation using the standalone individual installer Messenger.msi, try to install the following 3 programs too, all of which in different sub-folders inside the .cache directory.
   
   Contacts.msi (Contacts)
   dw20shared.msi (DW 2.0 Client)
   crt.msi (Microsoft Visual Studio Runtime)
   
   Tip: Contacts.msi is a must to avoid or fix 8000FFFF error.

After grabbing the Windows Live Messenger standalone silent installer, optionally user can uninstall the Windows Live Suite (all programs) from Control Panel, and install Messenger.msi (and Contacts.msi too) again to get rid of all other Windows Live components except WLM9, saving time and bandwidth in future installation.

The trick also work for all other Windows Live products such as Windows Live Sign-In Assistant (wllogin.msi), Windows Live Writer, Windows Live Mail ,Windows Live Toolbar, Windows Live Photo Gallery, Windows Live Family Safety, Segoe UI Font, Windows Live Call and Microsoft Office Outlook Connector.
 

This prevents code stripping or manipulation of code between the geshibot tags (using curly braces) in FCKeditor WYSIWYG. (or anyother specified tag)

Firstly make sure you have set Joomla's whitelist/blacklist thing properly as descibed in this article.

http://docs.joomla.org/Why_does_some_HTML_get_removed_from_articles_in_version_1.5.8%3F

The easiest way of checking this is to turn off your editor, paste some code in, save the article and see if joomla has stripped the code out.

Next choose FCKeditor as your WYSIWYG, install if needed.

To prevent any code in between the geshibot tags being stripped out we need to add a line of code to

/plugins/editors/fckeditor/fckconfig.js

search for (about line 66):

{code class="brush: text"}// FCKConfig.ProtectedSource.Add( /(]+>[\s|\S]*?<\/asp:[^\>]+>)|(]+\/>)/gi ) ; // ASP.Net style tags {/code}

right below it add:

{code class="brush: text"}FCKConfig.ProtectedSource.Add( /{geshibot[\s\S]*?}[\s\S]*?{\/geshibot}/g ) ; // Protects all code between GESHI tags{/code}

or another example using code and curly braces

{code class="brush: text"}FCKConfig.ProtectedSource.Add( /{code[\s\S]*?}[\s\S]*?{\/code}/g ) ; // Protects all code between code tags{/code}

Save file, empty you browser cache to make sure nothing is left. FCKeditor will now leave all code between the geshibot tags alone.

This code will allow you to specify the parameters of Geshibot in the first bracket aswell.

Please note, when you uninstall or upgrade this change will dissapear and will have to mod the file again. Also, the geshibot tags and the code between it will only be visible on the source page.

This technique can be used to protect other needed tags for FCKeditor

The following instructs FCKeditor to accept the tags <MYTAG> and <CUSTOM> . The following protects tags that are in the normal html entity style with the greater and lesser than signs

{code class="brush: text"}FCKConfig.ProtectedTags = 'MYTAG|CUSTOM' ;{/code}

Sage Line 50 Accounting never uninstalls completely and occasionally on upgrade will stop working with such sypmtoms as:

1. When sage is run it hangs on the splash screen
2. when Sage is run and then a company is selected it hangs on the splash screen

To solve this follow these steps:

1. Uninstall .Net Framework 2.0
2. Uninstall Sage
3. Goto C:\Program Files\Common Files and delete all sage folders
4. Delete C:\WINDOWS\sage.ini
5. Move/Delete C:\WINDOWS\SYSTEM32\sg*.* (I also turn company on in details and check for any further Sage files)
6. Rename Sage program directory, all data files are maintained here
7. Reboot PC
8. Install .Net Framework 2.0 of the Sage CD
9. Install Sage of the Sage CD
10. Reboot

Sage should now work. You can now also install any company data in to Sage. I would also install all updates.

STOP 0x0000007B: Inaccessible Boot Device occurs after you have imaged a harddrive or installed the harddrive in to a new PC with a different configuration.

This is caused by windows  not having the correct 'Boot Level' drivers installed to access the SATA or  the wrong IDE drivers are installed.

This can be fixed by one of the following. work through them in order.

1. Check in the BIOS for an option to set the onboard SATA to IDE mode
2. Use IDE merge to reset IDE drivers to default (via ERD 2005)
3. Use Driver Injection Tool to insert the correct drivers in to the offline windows installtion. BartPE and the TXTSETUP.OEM drivers are also required.
   Download Here (Local Mirror), DriverInjection GUI Homepage - The CD Forum
4. Do a repair install of windows, data will not be lost
5. Injecting massstorage drivers with MSSTMake - The CD Forum - Not Tried

If you have created a website and forgot to set the charset to UTF-8 and it has defaulted to Latin-1 then follow the instruictions below.

1. First make a back up of the database.
2. Find the line(s) that contains "SET NAMES latin1" and change that to "SET NAMES utf8".
3. Then, look at the table definition(s) and change "DEFAULT CHARSET=latin1" to "DEFAULT CHARSET=utf8".
4. Save the database
5. Set operations in phpmyadmin to UTF-8 (utf8_general_ci),
6. Reimport the database to the website

This also applies to other menu itmes.

It's a little obscure when first using Joomla...
In your Administrator portal, select Menus>Main Menu>Home>Parameters(System); there's a radio selection for "Show Page Title", select "No", and it will be removed.

Go to the Run item on the Start menum, and type:

regsvr32 <path & filename of dll or ocx>
 

or

1.Locate the file using windows explorer or My Computer. Alternatively search for the filename.

2.Hold down the shift key and right click on the file. Then click 'Open With...' from the menu.

3.An 'Open With' dialog box should appear. Click the button 'Other...'.

4.Navigate to your windows\system32 directory and select the file 'RegSvr32.exe'. Do a file search for it if you have trouble locating the exact folder. On Windows 2000 it is typically located in c:\WINNT\System32. Click Open to select the file. Then click OK on the 'Open With' dialog.

5.You should see a message indicating the file was successfully registered. If you see an error message, try restarting your computer and going through the above process again.

When you run iPrep you get a stack overflow error, even when using compatable equipment.

When you get a stack overflow just disable your IDE's in your bios

Symptoms

During text-mode Setup in Windows, your computer may stop responding (hang) when the "Setup is starting Windows" screen appears, and you may have to restart it.

NOTE: Hardware detection is occurring during this portion of Setup. Based on your computer's configuration, this process may take 30 minutes or longer. Be sure your computer is actually hung before you restart it. If you can restart your computer by pressing CTRL+ALT+DELETE, it is probably not hung.

Cause

This behavior can occur if Windows does not recognize or cannot configure the hardware in your computer.

Resolution

work around this behavior, use the following methods:

• Contact your computer manufacture to inquire about an updated Basic Input/Output System (BIOS).
• Modify your computer's BIOS the following ways:
  • Change the Plug and Play settings. For example, if Plug and Play functionality is currently being controlled by the BIOS, change it so it is controlled by the operating system.
  • Enable or disable Universal Serial Bus (USB) support.
  • Disable power management support.
  • Disable infrared support.
  • Disable all serial ports.
• Remove non-essential hardware devices one at a time. This includes a second video adapter, Small Computer System Interface (SCSI) adapters, modems, sound cards, network adapters, and other non-essential Industry Standard Architecture (ISA) adapters, Peripheral Component Interconnect (PCI) adapters, and PC Cards.
• Disconnect non-essential external devices and cables, such as backup devices, external hard disk drives, printers, and scanners.
• If you are using a notebook computer, verify that it is not currently in a docking station.
• Specify a different computer type when you start your computer. For additional information, please see the following article in the Microsoft Knowledge Base:
  
  214351  (http://support.microsoft.com/kb/214351/EN-US/ ) How to Specify a Specific or Third-Party HAL During Setup
• Using a text editor, disable unnecessary SCSI lines in the [SCSI.LOAD] section of the Txtsetup.sif file by typing a semicolon (;) at the beginning of each line.